Create
New tag definitions can only be created by the JEDI team. To request a new tag, you must submit a request via email with the required details.
Users cannot create tag definitions directly. All tag creation requests must be submitted to QuickLink Support for review and implementation.
Before You Request
Check if an existing tag already meets your needs — see the Overview page for a complete list of available tags, including system-generated ones.
How to Request a New Tag
📨 Ready to request a new tag?
Send us the details below and we'll take care of the rest.
Clicking the button opens a pre-filled email — just fill in the blanks and send.
What You'll Need to Provide
| Question | Valid Options | Example |
|---|---|---|
| Tag Name | UPPERCASE, no spaces | PROJECTNAME, TESTSTATUS, CUSTOMERINFO |
| Tag Type | string | number | boolean | enum | array | object | string |
| Description | Free text explaining what the tag is for | "Tracks which project the data read belongs to" |
| Allowed Values | (Only if type = enum) List of valid options to choose from | pending, passed, failed |
| Fields | (Only if type = object) See table below | See object example |
Tag Types Explained
| If you need... | Choose | What you can store |
|---|---|---|
| Text | string | Any text value, e.g. "My Project Name" |
| A number | number | Any numeric value, e.g. 12345 |
| Yes or No | boolean | true or false |
| Pick from a predefined list | enum | One value from your defined list, e.g. "passed" from ["pending", "passed", "failed"] |
| Multiple values | array | A list of values, e.g. ["value1", "value2"] |
| Complex data with multiple fields | object | An object with defined properties, e.g. { "name": "Test", "count": 5 } |
Object Field Types
When creating an object tag, each field needs a type:
| Field Type | Description | Example Value |
|---|---|---|
string | Text | "Test Name" |
number | Numeric | 42 |
boolean | Yes/No | true or false |
Request Examples
For basic types (string, number, boolean), just provide the name, type, and description:
| Type | Example Name | Example Description |
|---|---|---|
string | PROJECTNAME | The name of the project this data read belongs to |
number | TESTRUNID | A numeric identifier for test runs |
boolean | ISVALIDATED | Whether the data has been validated |
Enum Tag
For "pick from a list" tags, also specify the allowed values:
- Name:
TESTSTATUS - Type:
enum - Description: The status of the test
- Allowed values:
pending,passed,failed,skipped
Object Tag
For complex tags with multiple fields, describe each field:
- Name:
TESTINFO - Type:
object - Description: Detailed information about a test
- Fields:
| Field Name | Type | Description | Required? |
|---|---|---|---|
| TESTNAME | string | The name of the test | Yes |
| ITERATIONS | number | Number of test iterations | No |
| PASSED | boolean | Whether the test passed | Yes |
Just answer the questions in plain language using the email template. QuickLink Support will handle the technical formatting and configuration.
What Happens Next
- QuickLink Support reviews your request
- If approved, the JEDI team creates the tag definition
- You will be notified when the tag is available
- The new tag appears in QuickLink for assigning to data reads
Tag names are automatically converted to UPPERCASE when created (e.g., projectname → PROJECTNAME).